home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19951130-19960209
/
000104_news@columbia.edu_Wed Dec 13 21:22:40 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA09193
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun>); Thu, 14 Dec 1995 16:24:44 -0500
Received: (from news@localhost) by apakabar.cc.columbia.edu (8.6.12/8.6.12) id QAA02705 for kermit.misc@watsun; Thu, 14 Dec 1995 16:24:42 -0500
Newsgroups: comp.os.vms,comp.protocols.kermit.misc
Path: news.columbia.edu!panix!news.intercon.com!netnews.com!uhog.mit.edu!nntp.club.cc.cmu.edu!cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!newsfeed.rice.edu!news.sesqui.net!imci2!newsfeed.internetmci.com!portal.gmu.edu!hearst.acc.Virginia.EDU!murdoch!fulton.seas.Virginia.EDU!esh6h
From: esh6h@fulton.seas.Virginia.EDU (Erik Hatcher)
Subject: VMS C-Kermit (5A 190) .zip file transmission problems
X-Nntp-Posting-Host: fulton.seas.virginia.edu
Message-Id: <DJJnDs.Dpy@murdoch.acc.Virginia.EDU>
Sender: usenet@murdoch.acc.Virginia.EDU
Organization: University of Virginia
Date: Wed, 13 Dec 1995 21:22:40 GMT
Lines: 36
Xref: news.columbia.edu comp.os.vms:116453 comp.protocols.kermit.misc:4302
Apparently-To: kermit.misc@watsun.cc.columbia.edu
Hi,
We are using C-Kermit (version 5A 190) for OpenVMS, both
on the AXP and VAX platforms to automate file transfers
with several systems all running the same setup.
All file transmissions work fine except for .zip files.
All files are being transmitted using the "labeled" format.
.zip file transmissions completely "hang" the modems on
both ends with no system activity showing on either end
and it never times out or fails (causing some large phone bills!).
We are in the process of double checking all recommendations in
the C-Kermit documentation and CKVINS.DOC to see if there is
a system parameter that is causing our troubles, but wanted
to post to the Internet community to see if anyone has any
ideas or suggestions for us concerning this.
If this is not solved soon we will be investigating a more failproof
way to transmit files automatically.
All command procedures, etc have been taken out of the loop and a
straight log-on, initiate C-Kermit "server", drop back to the local
machine and do a C-Kermit "send" causes the "hang". And every once
in a while, but not often, the problem file actually makes it to
where it is supposed to go (could be system activity related).
Any and all help is greatly appreciated.
Thanks,
Erik Hatcher
--
Erik Hatcher
http://fulton.seas.virginia.edu/~esh6h